Artificial Reality Browser Configured to Trigger an Immersive Experience

ABSTRACT

Aspects of the disclosure are directed to an artificial reality (XR) browser configured to trigger an immersive experience. Implementations display an element at a browser chrome of the XR browser when an immersive experience is loaded. For example, the XR browser can include an application programming interface (API) that supports configuration of a browser chrome element by components of a webpage. The API call can cause the display of the browser chrome element, change a display property for the browser chrome element, or configure the browser chrome element in any other suitable manner. Upon receiving input at the browser chrome element (configured by the API call), the XR browser can transition from displaying a two-dimensional panel view of a webpage supported by loaded web resources (e.g., hypertext transfer protocol (HTTP) pages, graphic images, etc.) to a three-dimensional environment supported by preloaded immersive resources (e.g., three-dimensional models, graphic images, etc.)

TECHNICAL FIELD

The present disclosure is directed to an artificial reality browserconfigured to trigger an immersive experience.

BACKGROUND

Display systems can display content to users in a variety of formatsthat match user preferences or use cases. However, content can have avariety of display configurations, and effectively displaying content inaccordance with user selections and/or expectations remains a challenge.For example, web content that includes immersive experiences can have avariety of different configurations that are specific to design choice,implemented technology, model selection, or other suitableconfigurations. Due to this diversity, users can encounter unexpecteddisplay artifacts and/or navigation that fails to achieve intuitiveresults.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating an overview of devices on whichsome implementations of the present technology can operate.

FIG. 2A is a wire diagram illustrating a virtual reality headset whichcan be used in some implementations of the present technology.

FIG. 2B is a wire diagram illustrating a mixed reality headset which canbe used in some implementations of the present technology.

FIG. 2C is a wire diagram illustrating controllers which, in someimplementations, a user can hold in one or both hands to interact withan artificial reality environment.

FIG. 3 is a block diagram illustrating an overview of an environment inwhich some implementations of the present technology can operate.

FIG. 4 is a block diagram illustrating components which, in someimplementations, can be used in a system employing the disclosedtechnology.

FIG. 5 is a system diagram illustrating components for an artificialreality browser configured to trigger an immersive experience.

FIGS. 6A and 6B are diagrams for configuring an immersive experiencetriggered using an artificial reality browser.

FIGS. 7A, 7B, 7C, and 7D illustrate a series of diagrams that visualizean artificial reality browser configured to trigger an immersiveexperience.

FIG. 8 is a flow diagram illustrating a process used in someimplementations of the present technology for triggering an immersiveexperience at an artificial reality browser.

FIG. 9 is a flow diagram illustrating a process used in someimplementations of the present technology for triggering a menuconfigured immersive experience at an artificial reality browser.

The techniques introduced here may be better understood by referring tothe following Detailed Description in conjunction with the accompanyingdrawings, in which like reference numerals indicate identical orfunctionally similar elements.

DETAILED DESCRIPTION

Aspects of the present disclosure are directed to an artificial realitybrowser configured to trigger an immersive experience. A web browser candisplay content from a public network (e.g., the Internet) such as viathe host of a webpage, a content distribution network, or any othernetwork source of web content. The artificial reality browser can beconfigured to display both a two-dimensional display to a user, such asa standard webpage, and an immersive experience, such as athree-dimensional environment. A two-dimensional display, webpage, sitemay be a traditional 2D panel or may include some 3D content, such as a3D model that is provided in associating with the webpage or that isviewed with parallax effects. The web browser can retrieve/receiveresources according to the execution of code and/or scripts (e.g.,JavaScript) implemented as part of the webpage/web content.

In some implementations, immersive resources are loaded by theartificial reality browser (e.g., preloaded and/or dynamically loaded)after display of a webpage (e.g., homepage, landing page, or any othersuitable portion). For example, a landing page that includes limited webresources may load quickly while an immersive experience of athree-dimensional environment may take more time to load. Accordingly,the resources for the immersive experience may load while the landingpage (e.g., two-dimensional webpage) is displayed to the user. Any othersuitable webpage can be displayed while resources for an immersiveexperience are received, retrieved, initiated, and/or configured.

In some implementations, the artificial reality browser includes adisplay panel, which displays a two-dimensional webpage/contentretrieved from the public network, and a browser chrome, which displaysinterface/control elements for configuring and interacting with theartificial reality browser itself. For example, a button displayed inthe display panel can trigger a webpage function (e.g., navigation to anext webpage, submission of a web form, etc.) while a button displayedat the browser chrome can trigger browser functionality (e.g., bookmarkfunctions, user preferences, etc.).

Implementations display an element at the browser chrome of anartificial reality browser when an immersive experience is loaded (e.g.,is available to be experienced by the user). For example, the user canselect the displayed element (e.g., press a displayed button) andtrigger a transition from a two-dimensional panel-based display to athree-dimensional immersive experience. Implementations of theartificial reality browser include an application programming interface(API) that supports configuration of the browser chrome element byfiles, scripts, resources, or other suitable components of a webpage.For example, a component of the webpage can make an API call once therelevant resources for an immersive experience are loaded at theartificial reality browser. The API call can cause the display of thebrowser chrome element, change a display property for the browser chromeelement (e.g., transition from a greyed-out button, which represents aninactive status, to a colored button, which represents an activestatus), or configure the browser chrome element in any other suitablemanner.

In some implementations, in response to input at the browser chromeelement (e.g., a button press), the XR browser can display one or moreadditional elements for configuring the immersive experience. In oneexample, an additional element displayed can include a permissions panelwhere the user can provide permission to enter the immersive experienceand/or permission for access to the user's system (e.g., microphoneaccess, camera access, etc.) during the immersive experience. In anotherexample, an additional element displayed can include a configurationpanel where the user can provide input that configures the immersiveexperience, such as an initial location within a three-dimensionalenvironment the user will be taken to, a user presence for the immersiveexperience (e.g., avatar selection), or any other suitable input forconfiguring the immersive experience.

Upon receiving the input at the browser chrome element/initiating thetrigger for the immersive experience, the artificial reality browser cantransition from displaying a two-dimensional panel view of a webpagesupported by loaded web resources (e.g., hypertext transfer protocol(HTTP) pages, graphic images, etc.) to a three-dimensional environmentsupported by preloaded immersive resources (e.g., three-dimensionalmodels, graphic images, etc.) In some implementations, thetwo-dimensional panel view of a webpage is not displayed during theimmersive experience.

Embodiments of the disclosed technology may include or be implemented inconjunction with an artificial reality system. Artificial reality orextra reality (XR) is a form of reality that has been adjusted in somemanner before presentation to a user, which may include, e.g., virtualreality (VR), augmented reality (AR), mixed reality (MR), hybridreality, or some combination and/or derivatives thereof. Artificialreality content may include completely generated content or generatedcontent combined with captured content (e.g., real-world photographs).The artificial reality content may include video, audio, hapticfeedback, or some combination thereof, any of which may be presented ina single channel or in multiple channels (such as stereo video thatproduces a three-dimensional effect to the viewer). Additionally, insome embodiments, artificial reality may be associated withapplications, products, accessories, services, or some combinationthereof, that are, e.g., used to create content in an artificial realityand/or used in (e.g., perform activities in) an artificial reality. Theartificial reality system that provides the artificial reality contentmay be implemented on various platforms, including a head-mounteddisplay (HMD) connected to a host computer system, a standalone HMD, amobile device or computing system, a “cave” environment or otherprojection system, or any other hardware platform capable of providingartificial reality content to one or more viewers.

“Virtual reality” or “VR,” as used herein, refers to an immersiveexperience where a user's visual input is controlled by a computingsystem. “Augmented reality” or “AR” refers to systems where a user viewsimages of the real world after they have passed through a computingsystem. For example, a tablet with a camera on the back can captureimages of the real world and then display the images on the screen onthe opposite side of the tablet from the camera. The tablet can processand adjust or “augment” the images as they pass through the system, suchas by adding virtual objects. “Mixed reality” or “MR” refers to systemswhere light entering a user's eye is partially generated by a computingsystem and partially composes light reflected off objects in the realworld. For example, a MR headset could be shaped as a pair of glasseswith a pass-through display, which allows light from the real world topass through a waveguide that simultaneously emits light from aprojector in the MR headset, allowing the MR headset to present virtualobjects intermixed with the real objects the user can see. “Artificialreality,” “extra reality,” or “XR,” as used herein, refers to any of VR,AR, MR, or any combination or hybrid thereof.

Conventional browsers do not provide both two-dimensional and immersiveuser experiences and/or fail to provide an efficient mechanism fortransitioning between these experiences. For example, a conventionalbrowser that supports an immersive experience generally relies on theentry mechanism (e.g., triggering button or interface component) to bedefined and displayed by a webpage. In other words, the entry point isvariable based on where a web designer opts to place the entry pointand/or how the webpage is displayed at the browser. Due to thisvariance, users are often confused by how to trigger the immersiveexperience. In addition, conventional browsers lack a consistentmechanism that informs the user that an immersive experience isavailable, loaded, and/or ready for interaction. Thus, these browsersfail to provide an efficient user interface.

Implementations include an XR browser that permits a browser chromecomponent to be configured by web code/content according to an API call.For example, once an immersive experience is loaded (e.g., once theimmersive resources that define the experience are preloaded), an APIcall to the XR browser can modify a parameter of the browser chromecomponent. This modified parameter can modify the display of the browserchrome component, signaling to the user that the immersive experience isavailable, and serves as an entry point to the immersive experience.

Implementations of this configurable browser chrome component provide auser notice that an immersive experience is part of a web page, when animmersive experience has loaded, and a consistent entry point forimmersive experience(s). For example, multiple immersive experiences(e.g., across multiple third-party providers/designers) can support anentry point using the same (or a similar) browser chrome component andfunctionality. This consistency achieves an improved user interface andeliminates sources of user confusion.

Several implementations are discussed below in more detail in referenceto the figures. FIG. 1 is a block diagram illustrating an overview ofdevices on which some implementations of the disclosed technology canoperate. The devices can comprise hardware components of a computingsystem 100 that trigger an immersive display at an XR browser. Invarious implementations, computing system 100 can include a singlecomputing device 103 or multiple computing devices (e.g., computingdevice 101, computing device 102, and computing device 103) thatcommunicate over wired or wireless channels to distribute processing andshare input data. In some implementations, computing system 100 caninclude a stand-alone headset capable of providing a computer created oraugmented experience for a user without the need for external processingor sensors. In other implementations, computing system 100 can includemultiple computing devices such as a headset and a core processingcomponent (such as a console, mobile device, or server system) wheresome processing operations are performed on the headset and others areoffloaded to the core processing component. Example headsets aredescribed below in relation to FIGS. 2A and 2B. In some implementations,position and environment data can be gathered only by sensorsincorporated in the headset device, while in other implementations oneor more of the non-headset computing devices can include sensorcomponents that can track environment or position data.

Computing system 100 can include one or more processor(s) 110 (e.g.,central processing units (CPUs), graphical processing units (GPUs),holographic processing units (HPUs), etc.) Processors 110 can be asingle processing unit or multiple processing units in a device ordistributed across multiple devices (e.g., distributed across two ormore of computing devices 101-103).

Computing system 100 can include one or more input devices 120 thatprovide input to the processors 110, notifying them of actions. Theactions can be mediated by a hardware controller that interprets thesignals received from the input device and communicates the informationto the processors 110 using a communication protocol. Each input device120 can include, for example, a mouse, a keyboard, a touchscreen, atouchpad, a wearable input device (e.g., a haptics glove, a bracelet, aring, an earring, a necklace, a watch, etc.), a camera (or otherlight-based input device, e.g., an infrared sensor), a microphone, orother user input devices.

Processors 110 can be coupled to other hardware devices, for example,with the use of an internal or external bus, such as a PCI bus, SCSIbus, or wireless connection. The processors 110 can communicate with ahardware controller for devices, such as for a display 130. Display 130can be used to display text and graphics. In some implementations,display 130 includes the input device as part of the display, such aswhen the input device is a touchscreen or is equipped with an eyedirection monitoring system. In some implementations, the display isseparate from the input device. Examples of display devices are: an LCDdisplay screen, an LED display screen, a projected, holographic, oraugmented reality display (such as a heads-up display device or ahead-mounted device), and so on. Other I/O devices 140 can also becoupled to the processor, such as a network chip or card, video chip orcard, audio chip or card, USB, firewire or other external device,camera, printer, speakers, CD-ROM drive, DVD drive, disk drive, etc.

In some implementations, input from the I/O devices 140, such ascameras, depth sensors, IMU sensor, GPS units, LiDAR or othertime-of-flights sensors, etc. can be used by the computing system 100 toidentify and map the physical environment of the user while tracking theuser's location within that environment. This simultaneous localizationand mapping (SLAM) system can generate maps (e.g., topologies, girds,etc.) for an area (which may be a room, building, outdoor space, etc.)and/or obtain maps previously generated by computing system 100 oranother computing system that had mapped the area. The SLAM system cantrack the user within the area based on factors such as GPS data,matching identified objects and structures to mapped objects andstructures, monitoring acceleration and other position changes, etc.

Computing system 100 can include a communication device capable ofcommunicating wirelessly or wire-based with other local computingdevices or a network node. The communication device can communicate withanother device or a server through a network using, for example, TCP/IPprotocols. Computing system 100 can utilize the communication device todistribute operations across multiple network devices.

The processors 110 can have access to a memory 150, which can becontained on one of the computing devices of computing system 100 or canbe distributed across of the multiple computing devices of computingsystem 100 or other external devices. A memory includes one or morehardware devices for volatile or non-volatile storage, and can includeboth read-only and writable memory. For example, a memory can includeone or more of random access memory (RAM), various caches, CPUregisters, read-only memory (ROM), and writable non-volatile memory,such as flash memory, hard drives, floppy disks, CDs, DVDs, magneticstorage devices, tape drives, and so forth. A memory is not apropagating signal divorced from underlying hardware; a memory is thusnon-transitory. Memory 150 can include program memory 160 that storesprograms and software, such as an operating system 162, XR browsermanager 164, and other application programs 166. Memory 150 can alsoinclude data memory 170 that can include, e.g., web content, JavaScriptfiles, graphical files (e.g., bitmaps, .png, .jpeg, and the like),immersive content models (e.g., VFX models, three-dimensional models,mesh models, etc.), user data, avatar data, permissions and/orpreferences data, configuration data, settings, user options orpreferences, etc., which can be provided to the program memory 160 orany element of the computing system 100.

Some implementations can be operational with numerous other computingsystem environments or configurations. Examples of computing systems,environments, and/or configurations that may be suitable for use withthe technology include, but are not limited to, XR headsets, personalcomputers, server computers, handheld or laptop devices, cellulartelephones, wearable electronics, gaming consoles, tablet devices,multiprocessor systems, microprocessor-based systems, set-top boxes,programmable consumer electronics, network PCs, minicomputers, mainframecomputers, distributed computing environments that include any of theabove systems or devices, or the like.

FIG. 2A is a wire diagram of a virtual reality head-mounted display(HMD) 200, in accordance with some embodiments. The HMD 200 includes afront rigid body 205 and a band 210. The front rigid body 205 includesone or more electronic display elements of an electronic display 245, aninertial motion unit (IMU) 215, one or more position sensors 220,locators 225, and one or more compute units 230. The position sensors220, the IMU 215, and compute units 230 may be internal to the HMD 200and may not be visible to the user. In various implementations, the IMU215, position sensors 220, and locators 225 can track movement andlocation of the HMD 200 in the real world and in an artificial realityenvironment in three degrees of freedom (3DoF) or six degrees of freedom(6DoF). For example, the locators 225 can emit infrared light beamswhich create light points on real objects around the HMD 200. As anotherexample, the IMU 215 can include e.g., one or more accelerometers,gyroscopes, magnetometers, other non-camera-based position, force, ororientation sensors, or combinations thereof. One or more cameras (notshown) integrated with the HMD 200 can detect the light points. Computeunits 230 in the HMD 200 can use the detected light points toextrapolate position and movement of the HMD 200 as well as to identifythe shape and position of the real objects surrounding the HMD 200.

The electronic display 245 can be integrated with the front rigid body205 and can provide image light to a user as dictated by the computeunits 230. In various embodiments, the electronic display 245 can be asingle electronic display or multiple electronic displays (e.g., adisplay for each user eye). Examples of the electronic display 245include: a liquid crystal display (LCD), an organic light-emitting diode(OLED) display, an active-matrix organic light-emitting diode display(AMOLED), a display including one or more quantum dot light-emittingdiode (QOLED) sub-pixels, a projector unit (e.g., microLED, LASER,etc.), some other display, or some combination thereof.

In some implementations, the HMD 200 can be coupled to a core processingcomponent such as a personal computer (PC) (not shown) and/or one ormore external sensors (not shown). The external sensors can monitor theHMD 200 (e.g., via light emitted from the HMD 200) which the PC can use,in combination with output from the IMU 215 and position sensors 220, todetermine the location and movement of the HMD 200.

FIG. 2B is a wire diagram of a mixed reality HMD system 250 whichincludes a mixed reality HMD 252 and a core processing component 254.The mixed reality HMD 252 and the core processing component 254 cancommunicate via a wireless connection (e.g., a 60 GHz link) as indicatedby link 256. In other implementations, the mixed reality system 250includes a headset only, without an external compute device or includesother wired or wireless connections between the mixed reality HMD 252and the core processing component 254. The mixed reality HMD 252includes a pass-through display 258 and a frame 260. The frame 260 canhouse various electronic components (not shown) such as light projectors(e.g., LASERs, LEDs, etc.), cameras, eye-tracking sensors, MEMScomponents, networking components, etc.

The projectors can be coupled to the pass-through display 258, e.g., viaoptical elements, to display media to a user. The optical elements caninclude one or more waveguide assemblies, reflectors, lenses, mirrors,collimators, gratings, etc., for directing light from the projectors toa user's eye. Image data can be transmitted from the core processingcomponent 254 via link 256 to HMD 252. Controllers in the HMD 252 canconvert the image data into light pulses from the projectors, which canbe transmitted via the optical elements as output light to the user'seye. The output light can mix with light that passes through the display258, allowing the output light to present virtual objects that appear asif they exist in the real world.

Similarly to the HMD 200, the HMD system 250 can also include motion andposition tracking units, cameras, light sources, etc., which allow theHMD system 250 to, e.g., track itself in 3DoF or 6DoF, track portions ofthe user (e.g., hands, feet, head, or other body parts), map virtualobjects to appear as stationary as the HMD 252 moves, and have virtualobjects react to gestures and other real-world objects.

FIG. 2C illustrates controllers 270 (including controller 276A and276B), which, in some implementations, a user can hold in one or bothhands to interact with an artificial reality environment presented bythe HMD 200 and/or HMD 250. The controllers 270 can be in communicationwith the HMDs, either directly or via an external device (e.g., coreprocessing component 254). The controllers can have their own IMU units,position sensors, and/or can emit further light points. The HMD 200 or250, external sensors, or sensors in the controllers can track thesecontroller light points to determine the controller positions and/ororientations (e.g., to track the controllers in 3DoF or 6DoF). Thecompute units 230 in the HMD 200 or the core processing component 254can use this tracking, in combination with IMU and position output, tomonitor hand positions and motions of the user. The controllers can alsoinclude various buttons (e.g., buttons 272A-F) and/or joysticks (e.g.,joysticks 274A-B), which a user can actuate to provide input andinteract with objects.

In various implementations, the HMD 200 or 250 can also includeadditional subsystems, such as an eye tracking unit, an audio system,various network components, etc., to monitor indications of userinteractions and intentions. For example, in some implementations,instead of or in addition to controllers, one or more cameras includedin the HMD 200 or 250, or from external cameras, can monitor thepositions and poses of the user's hands to determine gestures and otherhand and body motions. As another example, one or more light sources canilluminate either or both of the user's eyes and the HMD 200 or 250 canuse eye-facing cameras to capture a reflection of this light todetermine eye position (e.g., based on set of reflections around theuser's cornea), modeling the user's eye and determining a gazedirection.

FIG. 3 is a block diagram illustrating an overview of an environment 300in which some implementations of the disclosed technology can operate.Environment 300 can include one or more client computing devices 305A-D,examples of which can include computing system 100. In someimplementations, some of the client computing devices (e.g., clientcomputing device 305B) can be the HMD 200 or the HMD system 250. Clientcomputing devices 305 can operate in a networked environment usinglogical connections through network 330 to one or more remote computers,such as a server computing device.

In some implementations, server 310 can be an edge server which receivesclient requests and coordinates fulfillment of those requests throughother servers, such as servers 320A-C. Server computing devices 310 and320 can comprise computing systems, such as computing system 100. Thougheach server computing device 310 and 320 is displayed logically as asingle server, server computing devices can each be a distributedcomputing environment encompassing multiple computing devices located atthe same or at geographically disparate physical locations.

Client computing devices 305 and server computing devices 310 and 320can each act as a server or client to other server/client device(s).Server 310 can connect to a database 315. Servers 320A-C can eachconnect to a corresponding database 325A-C. As discussed above, eachserver 310 or 320 can correspond to a group of servers, and each ofthese servers can share a database or can have their own database.Though databases 315 and 325 are displayed logically as single units,databases 315 and 325 can each be a distributed computing environmentencompassing multiple computing devices, can be located within theircorresponding server, or can be located at the same or at geographicallydisparate physical locations.

Network 330 can be a local area network (LAN), a wide area network(WAN), a mesh network, a hybrid network, or other wired or wirelessnetworks. Network 330 may be the Internet or some other public orprivate network. Client computing devices 305 can be connected tonetwork 330 through a network interface, such as by wired or wirelesscommunication. While the connections between server 310 and servers 320are shown as separate connections, these connections can be any kind oflocal, wide area, wired, or wireless network, including network 330 or aseparate public or private network.

FIG. 4 is a block diagram illustrating components 400 which, in someimplementations, can be used in a system employing the disclosedtechnology. Components 400 can be included in one device of computingsystem 100 or can be distributed across multiple of the devices ofcomputing system 100. The components 400 include hardware 410, mediator420, and specialized components 430. As discussed above, a systemimplementing the disclosed technology can use various hardware includingprocessing units 412, working memory 414, input and output devices 416(e.g., cameras, displays, IMU units, network connections, etc.), andstorage memory 418. In various implementations, storage memory 418 canbe one or more of: local devices, interfaces to remote storage devices,or combinations thereof. For example, storage memory 418 can be one ormore hard drives or flash drives accessible through a system bus or canbe a cloud storage provider (such as in storage 315 or 325) or othernetwork storage accessible via one or more communications networks. Invarious implementations, components 400 can be implemented in a clientcomputing device such as client computing devices 305 or on a servercomputing device, such as server computing device 310 or 320.

Mediator 420 can include components which mediate resources betweenhardware 410 and specialized components 430. For example, mediator 420can include an operating system, services, drivers, a basic input outputsystem (BIOS), controller circuits, or other hardware or softwaresystems.

Specialized components 430 can include software or hardware configuredto perform operations for triggering an immersive experience at an XRbrowser. Specialized components 430 can include XR browser 434,preloader 436, chrome controller 438, panel controller 440, andcomponents and APIs which can be used for providing user interfaces,transferring data, and controlling the specialized components, such asinterfaces 432. In some implementations, components 400 can be in acomputing system that is distributed across multiple computing devicesor can be an interface to a server-based application executing one ormore of specialized components 430. Although depicted as separatecomponents, specialized components 430 may be logical or othernonphysical differentiations of functions and/or may be submodules orcode-blocks of one or more applications.

XR browser 434 can display web content at a user system, such as atwo-dimensional webpage or a three-dimensional immersive experience.Implementations of XR browser 434 load web resources from a web host,content distribution network, cache, or any other suitable source of webcontent. The user system can be an XR system, a smartphone, or any othersuitable client device capable of rendering an immersive experience(e.g., three-dimensional environment).

XR browser 434 can include at least two components. A first componentcan be a browser component that includes a browser chrome and a secondcomponent can be a web display that displays web content. For example,the first component can include an interface for interacting with and/orconfiguring the browser itself. In some implementations, chromecontroller 438 can control the browser chrome component of XR browser434. The second component can display received/retrieved/stored webcontent at XR browser 434. For example, the second component can includea panel window that displays two-dimensional webpages. In anotherexample, the second component can include an immersive volume thatdisplays a three-dimensional environment for an immersive experience(e.g., a three-dimensional artificial reality environment).

In some implementations, XR browser 434 can run at least two portions ofcode. A first code portion can be browser code that implementsfunctionality for the XR browser 434 itself (e.g., functionality for thefirst component of XR browser 434) and a second code portion can be webcode that implements webpage/immersive experience functionality (e.g.,functionality for the second component of XR browser 434).Implementations of the browser code can be first-party code (e.g.,native code at the user system, cloud-based code for the XR browser, orother suitable first-party code) and implementations of the web code canbe third-party code (e.g., code received/retrieved from a web source).In some implementations, the browser code can expose an API to the webcode such that an API call from the web code can configure an element ofthe browser chrome (e.g., first component of XR browser 434). Forexample, after the web code loads the resources that support animmersive experience, the web code can make an API call that configuresan element at the browser chrome (e.g., a button).

Preloader 436 can preload and/or dynamically load web resources, such asweb resources that implement an immersive experience. In someimplementations, XR browser 434 can retrieve/receive one or morewebpages from a web host/web source and display a webpage, such as alanding webpage. For example, the user can navigate the landing webpage(or any other suitable webpage) while preloader 436 loads, in thebackground, resources that support an immersive experience.

Preloader 436 can be implemented by web code, a combination of browsercode and web code, or any other suitable code. For example, one or moreportions of JavaScript code can load immersive resources that implementthe immersive experience (e.g., retrieve the immersive resources from aweb source, configure/initialize the immersive resources using a script,etc.) Example immersive resources include JavaScript resources (e.g.,files, scripts, etc.), graphical resources (.jpeg, .png, .bitmap, etc.),model resources (e.g., three-dimensional models, mesh models, vfxmodels, etc.), binary resources (e.g., executable files), or any othersuitable immersive resources. Once preloader 436 completes the loadingof a set of immersive resources associated with an immersive experience,portions of the web code can execute an API call to the browsercode/chrome controller 438 to configure an element of the browserchrome, such as a button or other suitable interface element. Forexample, one or more “onload” methods implemented by the web code canreturn indication(s) that one or more resources are loaded, and the APIcall can be performed in response to these indication(s). In someimplementations, the API call and resultant configuration of the elementof the browser chrome (e.g., button) can indicate to a user that theimmersive experience is loaded and ready for user interaction.

Chrome controller 438 can control a chrome browser component of XRbrowser 434. The browser chrome can include interface elements (e.g.,buttons, menus, tabs, or other suitable interface elements) forconfiguring the XR browser 434. Example browser chrome elements includeback, forward, and refresh buttons, an address bar, one or morebookmarks, one or more menus and/or panels (e.g., user preferenceinterfaces, history interfaces, etc.) plug-in/add-on elements, and othersuitable browser chrome elements. In some implementations, chromecontroller 438 can expose an API such that web code can call the API andconfigure an element at the browser chrome.

For example, chrome controller 438 can receive the API call andconfigure a button at the browser chrome based on the API call. In someimplementations, web code can make the API call in response to immersiveresources being loaded and/or configured at XR browser 434. Chromecontroller 438 can set/modify a property for the button according to theAPI call. In one example, the button may not have been previouslydisplayed at the browser chrome, and the set/modified property can causethe button to be displayed. In another example, the button may have beendisplayed with an inactive status (e.g., greyed out, unable to receivepush/press input), and the set/modified property can cause the button tobe activated (e.g., cause a change of coloring for the button, change afunctionality for the button such that a push/press input can bereceived). In yet a further case, the button may be visible when thewebsite contains an immersive experience and can indicate a downloadprogress (e.g., status bar) for the immersive experience, becomingactionable to activate the immersive experience when the immersiveexperience content has been retrieved. Any other suitable element of thebrowser chrome and/or element property can be configurable by the APIcall.

In some implementations, in response to input received at the browserchrome, chrome controller 438 can cause an interface to be displayed,such as a menu or window. Input received at the displayed interface canconfigure the immersive experience/three-dimensional environment. Forexample, the interface can request permissions from a user, such aspermission to enter the immersive experience, permission to access oneor more devices at the user system (e.g., microphone, camera,controller, and the like), or other suitable permissions. Whenpermissions are granted by the user, web display controller 440 cantransition the web display from a two-dimensional webpage to theimmersive experience, and the device(s) can be accessed during theimmersive experience according to the granted permissions.

In another example, the user can provide configuration input via thedisplayed interface. The configuration input can include a locationwithin the immersive experience, a user presence (e.g., user avatar) forthe immersive experience, and other suitable configuration information.Web display controller 440 can transition the web display from atwo-dimensional webpage to the immersive experience according to theconfiguration input received at the interface. For example, theimmersive experience can be displayed at the specified location within athree-dimensional environment and/or a user's presence during theimmersive experience can be defined by the specified avatar/presenceinput.

Web display controller 440 can control a web display component of XRbrowser 434. For example, the web display component can display atwo-dimensional webpage and/or a three-dimensional environment (e.g., XRenvironment of the immersive experience). In some implementations, thetwo-dimensional webpage can be defined by received/retrieved webpagedata (e.g., HTTP files, JavaScript files, images, etc.) In someimplementations, the three-dimensional environment can be defined byreceived/retrieved immersive resources, such as one or more models(e.g., shells, vfx models, wireframes, etc.), graphic files (e.g.,backgrounds, images spread over wireframes, shells, and/or models,etc.), code (e.g., JavaScript, binary files, etc.), and other suitableimmersive resources.

Web display controller 440 can transition from display of thetwo-dimensional webpage to the three-dimensional environment (for theimmersive experience) at the web display component of XR browser 434,such as in response to user input received at an element of the browserchrome (e.g., button push/press, permission grants, etc.) In someimplementations, web display controller 440 can also transition fromdisplay of the three-dimensional environment to the two-dimensionaldisplay at the web display component of XR browser 434 in response touser input.

Implementations can improve transitions between a two-dimensionaldisplay (e.g., webpage display) and a three-dimensional display (e.g.,immersive experience) at an XR browser using a XR browser chromecomponent that can be configured by web code/content via an API call tothe XR browser. FIG. 5 is a system diagram illustrating components foran artificial reality browser configured to trigger an immersiveexperience. System 500 includes XR browser 502, browser chrome 504, webdisplay component 506, web resource(s) 508, immersive resource(s) 510,and chrome element 512.

XR browser 502 can include browser chrome 504 and web display component506. Browser chrome 504 can display interface elements (e.g., buttons,menus, forms, etc.) that configure the XR browser itself. Web displaycomponent 506 can display content received/retrieved from a data network(e.g., the Internet), such as web pages, immersive experiences (e.g.,three-dimensional environments), and/or other third-party web content.

In some implementations, web display component 506 can display one ormore webpages using web resource(s) 508 (e.g., HTTP files, JavaScriptfiles, images, and the like). For example, web resource(s) 508 can beloaded at XR browser 502 (e.g., received/retrieved from a host service,content delivery network, cache, or any other suitable source for webcontent), and two-dimensional webpages defined using web resource(s) 508can be displayed at web display component 506.

Implementations of XR browser 502 can preload immersive resource(s) 510(e.g., receive/retrieve from a host service, content delivery network,cache, or any other suitable source for web content, initialize,configure, or otherwise preload) while one or more webpage(s) aredisplayed at web display component 506. For example, XR browser 502 mayload web resource(s) 508 faster than immersive resource(s) 510, e.g., insome instances where the immersive resource(s) 510 are larger in sizethan web resource(s) 508 (and for other suitable reasons). After webresource(s) 508 are loaded and one or more webpages are displayed at webdisplay component 506, XR browser 502 can preload immersive resource(s)510 in the background. In this example, a user can navigate and/orinteract with the displayed webpages while immersive resource(s) 510 arebeing loaded.

Once XR browser 502 successfully loads immersive resource(s) 510, webcode that implements the webpages displayed at web display component 506can perform an API call to XR browser 502. The API call can configure acomponent of browser chrome 504. For example, the API call can set aproperty for chrome element 512. In some implementations, the API callcan set a display property for chrome element 512 (e.g., transition thedisplay from hidden/not displayed to displayed), set an interactionsetting for the chrome element (e.g., transition an inactive button thatcannot receive a press input—i.e., a “grayed-out” version, to an activebutton), or configure chrome element 512 in any other suitable manner.In some cases, the chrome element 512 can display an indication of theprocess of loading the immersive resource(s) 510, e.g., by showing thecomponent 512 as a status bar indicting the amount of the immersiveresource(s) 510 that have been preloaded.

FIG. 5 illustrates chrome element 512 as a button, however any othersuitable element can be implemented. After the API call configureschrome element 512, a display for the element can be modified. Forexample, chrome element 512 can be displayed at browser chrome 504(where the element was previously not displayed), chrome element 512 canundergo a color change (e.g., greyed out button to a colored button),text at chrome element 512 can be displayed/modified (e.g., blank textor text that indicates loading in progress can be modified to text thatindicates the immersive experience is loaded, such as “Loaded”, “Go”, orany other suitable text), or any other suitable display modification canoccur. The modification to the display of chrome element 512 canindicate to a user that the immersive experience is loaded and ready foruser interaction.

In some implementations, a user of XR browser 502 can provide input atchrome element 512 to trigger entry into the loaded immersiveexperience. For example, chrome element 512 can be a button and (aftermodification) a button press action can trigger XR browser 502 totransition from a two-dimensional display of a webpage to athree-dimensional display of an immersive experience. In someimplementations, browser chrome 504 and a panel that displayedtwo-dimensional webpages at XR browser 502 can be hidden (e.g., notdisplayed) during the immersive experience/display of thethree-dimensional environment.

In some implementations, a button press (or any other suitable input) atchrome element 512 (after modification) can cause XR browser 502 todisplay one or more additional interfaces to configure the immersiveexperience prior to entry. FIGS. 6A and 6B are diagrams for configuringan immersive experience triggered using an artificial reality browser.Diagrams 600A and 600B include XR browser 502, browser chrome 504, webdisplay component 506, chrome element 512, menu component 602, andpermissions component 604.

Diagram 600A illustrates that menu component 602 is displayed by XRbrowser 502 in response to input received at chrome element 512. Menucomponent 602 can display menu items for configuring the immersiveexperience according to user input. An example menu item can be alocation within the immersive experience at which the immersiveexperience with begin when loaded. In some implementations, a dropdownmenu (or other suitable prepopulated menu) that includes a set oflocations within the immersive experience/three-dimensional environmentcan be displayed to the user, and the user can select one of theselocations to configure the immersive experience.

Another example menu item can be a user's presence within the immersiveexperience. In some implementations, a dropdown menu (or other suitableprepopulated menu) that includes preconfigured/preloaded user presenceoptions (e.g., avatars, default avatars for the immersive experience,custom avatars configured for/by the user, etc.) can be displayed to theuser, and the user can select one of these user presence options toconfigure the immersive experience. In another implementation, the menuitem can generate a web form that permits the user to select a filelocation (e.g., local to the user's system, or in any other suitablelocation), and the selected file can define a user avatar. In thisexample, the user can upload a file that supports the user's presence inthe immersive experience.

Diagram 600B illustrates that permissions component 604 is displayed byXR browser 502 in response to input received at chrome element 512.Permissions component 604 can retrieve input from the user that grantspermissions related to the immersive experience. Example permissionsinclude: a) permission to enter the user into the immersive experience;b) permission to access devices on the user's system (e.g., camera(s),microphone(s), sensor(s), or other suitable devices); c) permission toaccess a user's social media information; d) permission to permit otherusers within the immersive experience/three-dimensional environment tocommunicate and/or interact with the user; or e) any other suitablepermissions.

Any other suitable element(s) (e.g., display panels, prompts, and thelike) can be implemented to receive configuration information and/orpermissions for the immersive experience form a user. Once the immersiveexperience is configured with options and/or permission, XR browser 502can transition from the two-dimensional display of a webpage to thethree-dimensional display of an immersive experience, e.g., asillustrated in FIGS. 7A-7D.

FIGS. 7A, 7B, 7C, and 7D illustrate a series of diagrams that visualizean artificial reality browser configured to trigger an immersiveexperience. Each of diagrams 700A, 700B, and 700C depict a display at XRbrowser 502 of FIG. 5 . Diagrams 700A, 700B, and 700C include browserchrome 504, web display component 506, and chrome element 512 of FIG. 5. In diagram 700A, a webpage is displayed at web display component 506.Browser chrome 504 displays an active chrome element 512, whichindicates that immersive resources have been preloaded by XR browser 502in some implementations.

Diagram 700B illustrates that a user interacting with a user system(e.g., XR system) has selected/pressed chrome element 512. Diagram 700Cillustrates that, in response, XR browser 502 displays permissionscomponent 604 of FIG. 6 . For example, the permissions component cansecure permissions from the user. Diagram 700D illustrates that, inresponse to the user selecting the “Go” button at permissions component604, a transition is provided from a two-dimensional webpage display toa three-dimensional immersive experience display at XR browser 502. Forexample, the XR browser 502 can display a three-dimensional environmentto provide the user with the immersive experience. In someimplementations, browser chrome 504 and/or a panel portion of displaycomponent 506 (e.g., a panel display for a two-dimensional webpage) arenot displayed during the immersive experience.

Those skilled in the art will appreciate that the components illustratedin FIGS. 1-5, 6A, 6B, 7A, 7B, 7C, and 7D described above, and in each ofthe flow diagrams discussed below, may be altered in a variety of ways.For example, the order of the logic may be rearranged, substeps may beperformed in parallel, illustrated logic may be omitted, other logic maybe included, etc. In some implementations, one or more of the componentsdescribed above can execute one or more of the processes describedbelow.

FIG. 8 is a flow diagram illustrating a process used in someimplementations of the present technology for triggering an immersiveexperience via an artificial reality browser. In some implementations,process 800 can be performed when loading a webpage at an XR browser.Process 800 can load an immersive experience (e.g., three-dimensionalenvironment) and trigger a display transition at an XR browser from atwo-dimensional webpage to a three-dimensional immersive experience.

At block 802, process 800 can display, at an XR browser, atwo-dimensional webpage according to received web resources that definethe webpage. For example, the XR browser can include a browser chromethat displays an interface for the XR browser and a web component thatdisplays web content according to web resources received/retrieved bythe XR browser. One or more webpage(s) can be displayed that are definedby web resources (e.g., HTTP pages, HTML, XML, JavaScript, images,links, etc.) received/retrieved by the XR browser, such as from a hostservice, content distribution network, cache, or any other suitablesource of web content. In some implementations, the displayed webpage isa home page or a landing page of a website.

At block 804, process 800 can preload immersive resources at the XRbrowser. In some implementations, the immersive resources can includeone or more JavaScript resources, graphical resources, model resources,binary resources, or any combination thereof. For example, the webresources that define the displayed webpage may be loaded faster thanthe immersive resources that define the immersiveexperience/three-dimensional environment, so the immersive resources maybe loaded in the background while the user interacts with the webresources. The XR browser can preload the immersive resources while thewebpage is displayed to the user and/or while the user interacts with ornavigates the displayed webpage.

At block 806, process 800 can determine whether an API call has beenreceived. For example, the received web resources or the preloadedimmersive resources can issue an API call to the XR browser, such aswhen the web site begins loading with the call to indicate the site hasimmersive content that is being preloaded or once an immersiveexperience is loaded and/or initialized. In some implementations, thewebpages are implemented by web code, and the web code can issue the APIcall once a set of immersive resources that define the immersiveexperience are identified or preloaded.

When the API call has been received, process 800 can progress to block810. When the API call has not been received, process 800 can progressto block 808. At block 808, process 800 can continue to display thetwo-dimensional webpage. For example, the XR browser can display thetwo-dimensional webpage until process 800 determines, at block 806, thatthe API call is received (or the user navigates away from the currentwebpage).

At block 810, process 800 can set a property for a browser chromecomponent in response to the API call. For example, the set property canmodify a display of the browser chrome component. In someimplementations, the modification to the display of the browser chromecomponent by the set property transitions the browser chrome componentfrom hidden to displayed. For example, the browser chrome component canbe a button, and the button may not be displayed by the browser chromeprior to the API call. In response to the API call and the set propertyof the button, the XR browser can dynamically display the button at thebrowser chrome.

In some implementations, the modification to the display of the browserchrome component by the set property transitions the browser chromecomponent from a non-interactive component that is not configured toreceive user input to an interactive component that is configured toreceive user input. For example, the browser chrome component can be abutton, and the button may be displayed in an inactive state (e.g.,greyed out, without a mouseover display modification, etc.) by thebrowser chrome prior to the API call. In response to the API call andthe set property of the button, the XR browser can dynamically modifythe display of button to indicate an active status (e.g., modify thedisplay color, text, activate a mouseover display modification, etc.).The browser chrome component associated with the API call can be anyother suitable component.

At block 812, process 800 can determine whether input is received at thebrowser chrome component. For example, a user can interact with thebrowser chrome component (e.g., press a button, check a box, doubleclick, grab, etc.). When input is received at the browser chromecomponent, process 800 can progress to block 814. When input is notreceived at the browser chrome component, process 800 can remain atblock 812 until the input is received at the browser chrome component.For example, the XR browser can continue to display the two-dimensionalwebpage and the modified browser chrome component (e.g., modifiedaccording to the property set at block 810) until process 800 determinesthat input is received at the browser chrome component.

While any block can be removed or rearranged in various implementations,blocks 814 and 816 are shown in dashed lines to indicate there arespecific instances where blocks 814 and/or 816 are skipped. At block814, process 800 can display one or more permission prompts at thebrowser chrome. For example, the permission prompts can retrieve userpermissions for the immersive experience, such as permission to enterthe user into the immersive experience, permission to access devices onthe user's system (e.g., camera(s), microphone(s), sensor(s), or othersuitable devices), permission to access a user's social mediainformation, permission to permit other users within the immersiveexperience/three-dimensional environment to communicate and/or interactwith the user, or any other suitable permissions.

At block 816, process 800 can determine whether permission to enter theimmersive experience is received from the user. When permission isreceived from the user, process 800 can progress to block 818. Whenpermission is not received, process 800 can loop back to block 814 untiluser permission is received.

At block 818, process 800 can trigger a display transition from thetwo-dimensional webpage to the immersive experience. The immersiveexperience can be displayed according to the preloaded immersiveresources. In some implementations, the immersive experience includes athree-dimensional environment. In some implementations, devices at aclient system that implement the XR browser are activated during thetriggered immersive experience in response to input relative to thepermission prompts. For example, the devices can include one or more ofa microphone, a camera, a controller, a sensor, or any combinationthereof.

FIG. 9 is a flow diagram illustrating a process used in someimplementations of the present technology for triggering a menuconfigured immersive experience at an artificial reality browser. Insome implementations, process 900 can be performed when loading awebpage at an XR browser. Process 900 can load and configure animmersive experience (e.g., three-dimensional environment) and trigger adisplay transition at an XR browser from a two-dimensional webpage to athree-dimensional immersive experience.

At block 902, process 900 can receive input at a browser chromecomponent. For example, the browser chrome component can be part of abrowser chrome of an XR browser. An API call (made by web code thatimplements webpage(s) displayed at the XR browser) can modify thebrowser chrome component. For example, the API call can be performedwhen a set of immersive resources are preloaded at the XR browser. Insome implementations, the modification to the browser chrome componentand the received input can be similar to the browser chrome componentand user input at blocks 810 and 812 of FIG. 8 .

At block 904, process 900 can display a menu in response to the inputreceived at the browser chrome component. For example, the menu caninclude configuration options for configuring the immersiveexperience/three-dimensional environment according to user input. Anexample menu item can be an initial location within the immersiveexperience. In some implementations, a dropdown menu (or other suitableprepopulated menu) that includes a set of locations within the immersiveexperience/three-dimensional environment can be displayed to the user,and the user can select one of these locations to configure theimmersive experience.

Another example menu item can be a user's presence within the immersiveexperience. In some implementations, a dropdown menu (or other suitableprepopulated menu) that includes preconfigured/preloaded user presenceoptions (e.g., avatars, default avatars for the immersive experience,custom avatars configured for/by the user, etc.) can be displayed to theuser, and the user can select one of these user presence options (or aset of avatar configuration options—e.g., styles, face shape, skin tone,etc.) to configure the immersive experience. In another implementation,the menu item can generate a web form that permits the user to select anavatar definition object location (e.g., local to the user's system,cloud based, or in any other suitable location), and the selected avatardefinition object can control how the user appears in the immersiveexperience. In this example, the user's avatar is dynamically loaded atthe XR browser for the immersive experience and/or the user can uploadan avatar definition object that supports the user's presence in theimmersive experience.

At block 906, process 900 can determine whether menu responses arereceived. For example, the user may select one or more options for theimmersive experience, or opt not to make selections at the displayedmenu. When menu responses are received, process 900 can progress toblock 910. When menu responses are not received, process 900 canprogress to block 908.

At block 908, process 900 can select default configuration options forthe immersive experience. For example, in the absence of userselections, default locations and/or default user presence options canconfigure the immersive experience. The default options can be genericdefault options for several users or default options stored for thespecific user (e.g., based on historic data stored about the user'sinteractions with the immersive experience/three-dimensionalenvironment).

At block 910, process 900 can configure the immersive experienceaccording to the configuration options. For example, user input canselect a location for the immersive experience within athree-dimensional environment, a user presence for the immersiveexperience, or other suitable configuration options. In another example,one or more default options can be selected for the immersive experiencewhen the user opts not to make one or more selections. Configuring theimmersive experience can include loading/initializing thethree-dimensional environment at the selected location and/orloading/initializing the user's presence selection/avatar. At block 912,process 900 can trigger a transition to the immersive experienceaccording to the configuration. For example, the XR browser can displaythe user's presence according to the selection at the selected locationin a three-dimensional environment that implements the immersiveexperience.

Reference in this specification to “implementations” (e.g., “someimplementations,” “various implementations,” “one implementation,” “animplementation,” etc.) means that a particular feature, structure, orcharacteristic described in connection with the implementation isincluded in at least one implementation of the disclosure. Theappearances of these phrases in various places in the specification arenot necessarily all referring to the same implementation, nor areseparate or alternative implementations mutually exclusive of otherimplementations. Moreover, various features are described which may beexhibited by some implementations and not by others. Similarly, variousrequirements are described which may be requirements for someimplementations but not for other implementations.

As used herein, being above a threshold means that a value for an itemunder comparison is above a specified other value, that an item undercomparison is among a certain specified number of items with the largestvalue, or that an item under comparison has a value within a specifiedtop percentage value. As used herein, being below a threshold means thata value for an item under comparison is below a specified other value,that an item under comparison is among a certain specified number ofitems with the smallest value, or that an item under comparison has avalue within a specified bottom percentage value. As used herein, beingwithin a threshold means that a value for an item under comparison isbetween two specified other values, that an item under comparison isamong a middle-specified number of items, or that an item undercomparison has a value within a middle-specified percentage range.Relative terms, such as high or unimportant, when not otherwise defined,can be understood as assigning a value and determining how that valuecompares to an established threshold. For example, the phrase “selectinga fast connection” can be understood to mean selecting a connection thathas a value assigned corresponding to its connection speed that is abovea threshold.

As used herein, the word “or” refers to any possible permutation of aset of items. For example, the phrase “A, B, or C” refers to at leastone of A, B, C, or any combination thereof, such as any of: A; B; C; Aand B; A and C; B and C; A, B, and C; or multiple of any item such as Aand A; B, B, and C; A, A, B, C, and C; etc.

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described above.Specific embodiments and implementations have been described herein forpurposes of illustration, but various modifications can be made withoutdeviating from the scope of the embodiments and implementations. Thespecific features and acts described above are disclosed as exampleforms of implementing the claims that follow. Accordingly, theembodiments and implementations are not limited except as by theappended claims.

Any patents, patent applications, and other references noted above areincorporated herein by reference. Aspects can be modified, if necessary,to employ the systems, functions, and concepts of the various referencesdescribed above to provide yet further implementations. If statements orsubject matter in a document incorporated by reference conflicts withstatements or subject matter of this application, then this applicationshall control.

1. A method for triggering an immersive experience at an artificialreality (XR) browser, the method comprising: displaying, at the XRbrowser, a two-dimensional webpage according to received web resourcesthat define the webpage, wherein the XR browser comprises a browserchrome that displays an interface for the XR browser and a web componentthat displays web content according to web resources received by the XRbrowser; preloading a plurality of immersive resources at the XRbrowser, the immersive resources comprising one or more JavaScriptresources, graphical resources, model resources, binary resources, orany combination thereof; receiving, from the received web resources orthe preloaded immersive resources, an application programming interfacecall (API) that indicates the immersive resources are preloaded; settinga property for a browser chrome component in response to the API call,wherein the set property modifies a display of the browser chromecomponent; and triggering, based on input relative to the browser chromecomponent, a display transition from the two-dimensional webpage to theimmersive experience, wherein the immersive experience is displayedaccording to the preloaded immersive resources.
 2. The method of claim1, wherein the browser chrome component comprises a button and the inputrelative to the browser chrome component comprises a button press. 3.The method of claim 1, wherein the modification to the display of thebrowser chrome component by the set property comprises a) transitioningthe browser chrome component from hidden to displayed; or b)transitioning the browser chrome component from a non-interactivecomponent that is not configured to receive user input to an interactivecomponent that is configured to receive user input.
 4. The method ofclaim 1, further comprising: displaying, based on the input relative tothe browser chrome component, a menu at the browser chrome, the menuincluding parameters for the immersive experience.
 5. The method ofclaim 4, wherein at least one parameter of the menu comprises a userpresence parameter, and a user avatar is included in the triggeredimmersive experience according to input relative to the user presenceparameter of the menu.
 6. The method of claim 5, wherein the user avataris dynamically loaded at the XR browser for the immersive experience inresponse to the input relative to the user presence parameter of themenu.
 7. The method of claim 4, wherein at least one parameter of themenu comprises a location parameter, and a display location within thetriggered immersive experience is defined by input relative to thelocation parameter of the menu.
 8. The method of claim 1, furthercomprising: displaying, based on the input relative to the browserchrome component, one or more permission prompts at the browser chrome,wherein devices at a client system that implement the XR browser areactivated during the triggered immersive experience in response to inputrelative to the permission prompts.
 9. The method of claim 8, whereinthe devices include one or more of a microphone, a camera, a controller,a sensor, or any combination thereof.
 10. The method of claim 1, whereinthe immersive experience comprises a three-dimensional environment. 11.A computer-readable storage medium storing instructions that, whenexecuted by a computing system, cause the computing system to perform aprocess for triggering an immersive experience at an artificial reality(XR) browser, the process comprising: displaying, at the XR browser, atwo-dimensional webpage according to received web resources that definethe webpage, wherein the XR browser comprises a browser chrome thatdisplays an interface for the XR browser and a web component thatdisplays web content according to web resources received by the XRbrowser; preloading a plurality of immersive resources at the XRbrowser; receiving, from the received web resources or the preloadedimmersive resources, an application programming interface call (API)that indicates the immersive resources are preloaded; setting a propertyfor a browser chrome component in response to the API call, wherein theset property modifies a display of the browser chrome component; andtriggering, based on input relative to the browser chrome component, adisplay transition from the two-dimensional webpage to the immersiveexperience, wherein the immersive experience is displayed according tothe preloaded immersive resources.
 12. The computer-readable storagemedium of claim 11, wherein the browser chrome component comprises abutton and the input relative to the browser chrome component comprisesa button press.
 13. The computer-readable storage medium of claim 11,wherein the modification to the display of the browser chrome componentby the set property comprises a) transitioning the browser chromecomponent from hidden to displayed; or b) transitioning the browserchrome component from a non-interactive component that is not configuredto receive user input to an interactive component that is configured toreceive user input.
 14. The computer-readable storage medium of claim11, wherein the process further comprises: displaying, based on theinput relative to the browser chrome component, a menu at the browserchrome, the menu including parameters for the immersive experience. 15.The computer-readable storage medium of claim 14, wherein at least oneparameter of the menu comprises a user presence parameter, and a useravatar is included in the triggered immersive experience according toinput relative to the user presence parameter of the menu.
 16. Thecomputer-readable storage medium of claim 15, wherein the user avatar isdynamically loaded at the XR browser for the immersive experience inresponse to the input relative to the user presence parameter of themenu.
 17. The computer-readable storage medium of claim 14, wherein atleast one parameter of the menu comprises a location parameter, and adisplay location within the triggered immersive experience is defined byinput relative to the location parameter of the menu.
 18. Thecomputer-readable storage medium of claim 11, wherein the processfurther comprises: displaying, based on the input relative to thebrowser chrome component, one or more permission prompts at the browserchrome, wherein devices at a client system that implement the XR browserare activated during the triggered immersive experience in response toinput relative to the permission prompts, wherein the devices includeone or more of a microphone, a camera, a controller, a sensor, or anycombination thereof.
 19. The computer-readable storage medium of claim11, wherein the immersive experience comprises a three-dimensionalenvironment.
 20. A computing system for triggering an immersiveexperience at an artificial reality (XR) browser, the computing systemcomprising: one or more processors; and one or more memories storinginstructions that, when executed by the one or more processors, causethe computing system to perform a process comprising: displaying, at theXR browser, a two-dimensional webpage according to received webresources that define the webpage, wherein the XR browser comprises abrowser chrome that displays an interface for the XR browser and a webcomponent that displays web content according to web resources receivedby the XR browser; preloading a plurality of immersive resources at theXR browser; receiving, from the received web resources or the preloadedimmersive resources, an application programming interface call (API)that indicates the immersive resources are preloaded; setting a propertyfor a browser chrome component in response to the API call, wherein theset property modifies a display of the browser chrome component; andtriggering, based on input relative to the browser chrome component, adisplay transition from the two-dimensional webpage to the immersiveexperience, wherein the immersive experience is displayed according tothe preloaded immersive resources.